System and method for managing feature enablement in an information handling system

ABSTRACT

A system to manage a key license includes an information handling system having non-volatile memory accessible to a processor. The non-volatile memory stores feature enablement information related to a feature that the information handling system is adapted to provide. The non-volatile memory stores instructions that are accessible to the processor and executable by the processor to send the feature enablement information related to the feature to an external system after the information handling system is deployed, and to request the feature enablement information, or other feature enablement information related to the feature, from the external system in response to receiving a request for the information handling system to provide the feature.

FIELD OF THE DISCLOSURE

This disclosure relates generally to methods and systems for managingfeature enablement in an information handling system.

DESCRIPTION OF THE RELATED ART

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements can varybetween different applications, information handling systems can alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allow forinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software components that can be configured to process, store, andcommunicate information and can include one or more computer systems,data storage systems, and networking systems.

BRIEF DESCRIPTION OF THE DRAWINGS

Skilled artisans appreciate that elements in the figures are illustratedfor simplicity and clarity and have not necessarily been drawn to scale.For example, the dimensions of some of the elements in the figures maybe exaggerated or minimized relative to other elements to help toimprove understanding of embodiments of the disclosed apparatus.Embodiments incorporating teachings of the present disclosure areillustrated and described with respect to the drawings presented herein.

FIG. 1 is a diagram illustrating a particular embodiment of a system tomanage feature enablement in an information handling system;

FIG. 2 is a diagram illustrating another particular embodiment of asystem to manage feature enablement in an information handling system;

FIG. 3 is a diagram illustrating a further particular embodiment of asystem to manage feature enablement in an information handling system;

FIG. 4 is a flow diagram illustrating a particular embodiment of amethod of managing feature enablement in an information handling system;

FIG. 5 is a flow diagram illustrating another particular embodiment of amethod of managing feature enablement in an information handling system;

FIG. 6 is a flow diagram illustrating an additional particularembodiment of a method of managing feature enablement in an informationhandling system; and

FIG. 7 is a flow diagram illustrating a further particular embodiment ofa method of managing feature enablement in an information handlingsystem.

The use of the same reference symbols in different figures indicatessimilar or identical items.

DETAILED DESCRIPTION

The following description in combination with the figures is provided toassist in understanding the teachings disclosed herein. The followingdiscussion will focus on specific implementations and embodiments of theteachings. This focus is provided to assist in describing the teachingsand should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can certainlybe utilized in this application. The teachings can also be utilized inother applications and with several different types of architecturessuch as distributed computing architectures, client/serverarchitectures, or middleware server architectures and associatedcomponents.

For purposes of this disclosure, an information handling system caninclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a PDA, aconsumer electronic device, a network server or storage device, a switchrouter, wireless router, or other network communication device, or anyother suitable device and can vary in size, shape, performance,functionality, and price. The information handling system can includememory (volatile (e.g. random access memory, etc.), nonvolatile (readonly memory, flash memory etc.) or any combination thereof), one or moreprocessing resources, such as a central processing unit (CPU), hardwareor software control logic, or any combination thereof. Additionalcomponents of the information handling system can include one or morestorage devices, one or more communications ports for communicating withexternal devices as well as various input and output (I/O) devices, suchas a keyboard, a mouse, a video display, or any combination thereof. Theinformation handling system can also include one or more buses operableto transmit communications between the various hardware components.

Although referred to as a “device,” the device may be configured ashardware, firmware, software, or any combination thereof For example,the device may be hardware such as, for example, an integrated circuit(such as an Application Specific Integrated Circuit (ASIC), a FieldProgrammable Gate Array (FPGA), a structured ASIC, or a device embeddedon a larger chip), a card (such as a Peripheral Component Interface(PCI) card, a PCI-express card, a Personal Computer Memory CardInternational Association (PCMCIA) card, or other such expansion card),or a system (such as a motherboard, a system-on-a-chip (SoC), or astand-alone device). Similarly, the device could be firmware (such asany software running on an embedded device, a Pentium class or PowerPC™brand processor, or other such device) or software (such as any softwarecapable of operating in the relevant environment). The device could alsobe a combination of any of the foregoing examples of hardware, firmware,or software.

Devices or programs that are in communication with one another need notbe in continuous communication with each other unless expresslyspecified otherwise. In addition, devices or programs that are incommunication with one another may communicate directly or indirectlythrough one or more intermediaries.

Embodiments discussed below describe, in part, distributed computingsolutions that manage all or part of a communicative interaction betweennetwork elements. In this context, a communicative interaction may beintending to send information, sending information, requestinginformation, receiving information, receiving a request for information,or any combination thereof. As such, a communicative interaction couldbe unidirectional, bidirectional, multi-directional, or any combinationthereof. In some circumstances, a communicative interaction could berelatively complex and involve two or more network elements. Forexample, a communicative interaction may be “a conversation” or seriesof related communications between a client and a server—each networkelement sending and receiving information to and from the other.Whatever form the communicative interaction takes, the network elementsinvolved need not take any specific form. A network element may be anode, a piece of hardware, software, firmware, middleware, some othercomponent of a computing system, or any combination thereof.

In the description below, a flow-charted technique may be described in aseries of sequential actions. The sequence of the actions and the partyperforming the steps may be freely changed without departing from thescope of the teachings. Actions may be added, deleted, or altered inseveral ways. Similarly, the actions may be re-ordered or looped.Further, although processes, methods, algorithms or the like may bedescribed in a sequential order, such processes, methods, algorithms, orany combination thereof may be operable to be performed in alternativeorders. Further, some actions within a process, method, or algorithm maybe performed simultaneously during at least a point in time (e.g.,actions performed in parallel), can also be performed in whole, in part,or any combination thereof.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of features is notnecessarily limited only to those features but may include otherfeatures not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive-or and not to an exclusive-or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

Also, the use of “a” or “an” is employed to describe elements andcomponents described herein. This is done merely for convenience and togive a general sense of the scope of the invention. This descriptionshould be read to include one or at least one and the singular alsoincludes the plural, or vice versa, unless it is clear that it is meantotherwise. For example, when a single device is described herein, morethan one device may be used in place of a single device. Similarly,where more than one device is described herein, a single device may besubstituted for that one device.

Unless otherwise defined, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this invention belongs. Although methods and materialssimilar or equivalent to those described herein can be used in thepractice or testing of embodiments of the present invention, suitablemethods and materials are described below. All publications, patentapplications, patents, and other references mentioned herein areincorporated by reference in their entirety, unless a particular passageis cited. In case of conflict, the present specification, includingdefinitions, will control. In addition, the materials, methods, andexamples are illustrative only and not intended to be limiting.

To the extent not described herein, many details regarding specificmaterials, processing acts, and circuits are conventional and may befound in textbooks and other sources within the computing, electronics,and software arts.

FIG. 1 illustrates a particular embodiment of a system 100 to managefeature enablement in an information handling system. The system 100includes a chassis 102. A plurality of information handling systems,such as blade server 104 and blade server 106, are coupled to the serverchassis 102. One or more of the information handling systems communicatewith a network 108, such as the Internet or a private network, directlyor via a network interface at the chassis 102. Another informationhandling system, such as the other server 110 can also communicate withthe network 108. The system 100 also includes a feature enablementinformation management system, such as a key license management system(KLMS) 112.

In a particular embodiment, the blade server 106 is deployed at thechassis 102 and powers on. The blade server 106 is adapted to detect theKLMS system 112 via a network 108. The blade server 106 is adapted tosend feature enablement information 114, to the KLMS system 112 via thenetwork 108. The feature enablement information 114 can include a keylicense, a digital certificate, a password, a software token, otherfeature enablement information adapted to prevent unauthorized access toa feature that the blade server 106 is adapted to provide, or anycombination thereof. The feature enablement information 114 is stored atnon-volatile memory, such as Basic Input/Output System (BIOS) hardware,other platform-level hardware that stores firmware information, or othernon-volatile memory, at the blade server 106. Further, the featureenablement information 114 is associated with a feature that the bladeserver 106 is adapted to provide. In another embodiment, the bladeserver 106 is adapted to send a plurality of feature enablementinformation components, such as a plurality of key licenses to the KLMSsystem 112, where each feature enablement information component isassociated with one of a plurality of features that the blade server 106is adapted to provide, such as an application, utility, service, upgradeor other feature.

The blade server 106 is adapted to receive a request for a feature, suchas the feature associated with the feature enablement information 114sent to the KLMS system 112, or another feature associated with otherfeature enablement information. For example, the blade server 106 canreceive a request from a personal computing device (not shown) via alocal area network (not shown) for a particular application or otherfeature. In response, the blade server 106 is adapted to request featureenablement information related to the requested feature from the KLMSsystem 112. The blade server 106 is adapted to provide the requestedfeature to the personal computing device after the feature enablementinformation related to the requested feature is received from the KLMSsystem 112. Further, the blade server 106 is adapted to not provide therequested feature when the feature enablement information is notreceived from the KLMS system 112, such as when a maximum number of keylicenses or other feature enablement information components related tothe feature are being used by a customer or other party associated withthe blade server 106. In an illustrative embodiment, the blade server106 can be adapted to send an error message to the requesting systemwhen the feature enablement information is not received from the KLMSsystem 112.

The KLMS system 112 is adapted to detect a deployed information handlingsystem, such as the blade server 106, via the network. In oneembodiment, the KLMS system 112 can be adapted to discover the bladeserver 106. In another embodiment, the blade server 106 can discover theKLMS system 112 and inform the KLMS system 112 that the blade server 106has been deployed at a customer premises, for example. The KLMS system112 is adapted to receive and store the feature enablement information114. Further, the KLMS system 112 is adapted to associate the featureenablement information 114 with a feature that the blade server 106 isadapted to provide. In a particular embodiment, the KLMS system 112 canbe adapted to adjust a maximum number of key licenses or other featureenablement information components related to the feature that areavailable to a customer or other party associated with the blade server106. For instance, the KLMS system 112 can be adapted to set the maximumnumber at an integer (e.g., one) or to increment a previous maximumnumber by an integer.

The KLMS system 112 is adapted to receive a request for the featureenablement information 114. The request can be received from the bladeserver 106 or another requesting system, such as the other server 110 orthe blade server 104. In a particular embodiment, the KLMS system 112 isadapted to determine whether a maximum number of key licenses or otherfeature enablement information components related to the feature, isbeing used by the party associated with the blade server 106 or otherrequesting system. Further, the KLMS system 112 is adapted to notprovide the feature enablement information 114 when a maximum number offeature enablement information components is being used for the featureby the party. In a particular embodiment, the KLMS system 112 can beadapted to send an error message to the blade server or other requestingsystem when it does not provide the feature enablement information.

On the other hand, the KLMS system 112 is adapted to provide the featureenablement information 114 to the requesting system after the KLMSsystem 112 determines that fewer than a maximum number of key licensesor other feature enablement information components related to thefeature is being used by the party. In a particular embodiment, the KLMSsystem 112 can be adapted to increment a number of key licenses or otherfeature enablement information components used for the feature by theparty after providing the feature enablement information 114 to therequesting system, such as after the feature enablement information 114is installed at the requesting system. In an illustrative embodiment,the KLMS system 112 can be adapted to determine whether the featureenablement information 114 has been released back to the KLMS system 112by the requesting system and to decrement the number of key licenses orother feature enablement information components used for the feature bythe party.

FIG. 2 illustrates another particular embodiment of a system 200 tomanage feature enablement in an information handling system. The system200 includes a chassis 202. A plurality of information handling systems,such as blade server 204 and blade server 206, are coupled to the serverchassis 202. One or more of the plurality of information handlingsystems communicate with a chassis management system 208.

In a particular embodiment, the blade server 206 is deployed at thechassis 202 and powers on. The blade server 206 can be adapted to detectthe chassis management system 208. For instance, the blade server 206can be adapted to discover the chassis management system 208 or to bediscovered and contacted by the chassis management system 208. The bladeserver 206 is adapted to send a key license 214 to the chassismanagement system 208. In other embodiments, feature enablementinformation other than a key license can be sent. The key license 214 isstored at non-volatile memory, such as Basic Input/Output System (BIOS)hardware, at the blade server 206. Further, the key license 214 isassociated with a feature that the blade server 206 is adapted toprovide. In another embodiment, the blade server 206 is adapted to senda plurality of key licenses to the chassis management system 208, whereeach key license is associated with one of a plurality of features thatthe blade server 206 is adapted to provide.

The blade server 206 is adapted to receive a request for a feature, suchas the feature associated with the key license 214 sent to the chassismanagement system 208, or another feature associated with another keylicense. In response, the blade server 206 is adapted to request a keylicense related to the requested feature from the chassis managementsystem 208. The blade server 206 is adapted to provide the requestedfeature to a requesting device after the key license related to therequested feature is received from the chassis management system 208.Further, the blade server 206 is adapted to not provide the requestedfeature when the requested key license is not received from the chassismanagement system 208.

The chassis management system 208 is adapted to detect a deployedinformation handling system, such as the blade server 206. In oneembodiment, the chassis management system 208 can be adapted to discoverthe blade server 206. In another embodiment, the blade server 206 candiscover the chassis management system 208 and inform the chassismanagement system 208 that the blade server 206 has been deployed at thechassis 202. The chassis management system 208 is adapted to receive andstore the key license 214. Further, the chassis management system 208 isadapted to associate the key license 214 with a feature that the bladeserver 206 is adapted to provide. In a particular embodiment, thechassis management system 208 can be adapted to adjust a maximum numberof key licenses for the feature that are available at the chassismanagement system 208. For instance, the chassis management system 208can be adapted to set the maximum number at an integer (e.g., one) orincrement a previous maximum number by an integer.

The chassis management system 208 is adapted to receive a request forthe key license 214. The request can be received from the blade server206 or another requesting system, such as the blade server 204. Thechassis management system 208 is adapted to determine whether a maximumnumber of key licenses is being used for the feature. Further, thechassis management system 208 is adapted to not provide the key license214 when a maximum number of key licenses is being used for the feature.In a particular embodiment, the chassis management system 208 can beadapted to send an error message to the requesting system.

On the other hand, the chassis management system 208 is adapted toprovide the key license 214 to the requesting system after the chassismanagement system 208 determines that fewer than a maximum number of keylicenses are being used for the feature. In a particular embodiment, thechassis management system 208 can be adapted to increment a number ofkey licenses used for the feature after providing the key license 214 tothe requesting system. In an illustrative embodiment, the chassismanagement system 208 can be adapted to determine whether the keylicense 214 has been released back to the chassis management system 208by the requesting system and to decrement the number of key licensesused for the feature.

FIG. 3 illustrates an additional particular embodiment of a system 300to manage feature enablement in an information handling system. Thesystem 300 includes an information handling system, such as a server302, which communicates with an external system 322, such as a featureenablement information management system (e.g., the KLMS system 112illustrated in FIG. 1). In another embodiment, the external system 322can include a chassis management system (e.g., the chassis managementsystem 208 illustrated in FIG. 2). The server 302 includes a processor304; non-volatile memory, such as Basic Input/Output System (BIOS)hardware 306 that stores BIOS code accessible to the processor 304; andan interface 308 that facilitates communication between the server 302and a network, or between the server 302 and a chassis (not shown).

The BIOS hardware 306 includes platform-level instructions that areexecutable by the processor 304 to perform various functions of theserver 302 with respect to managing feature enablement information. Forinstance, the BIOS hardware 306 can store BIOS code that includes a keylicense 310 related to a feature. In a particular embodiment, theplatform-level hardware/firmware 306 also includes discoveryinstructions 312 that are executable by the processor 304 to discoverthe external system 322 via a network, such as the Internet, when theserver 302 is deployed. In another embodiment, where the external system322 is a chassis management system, the discovery instructions 312 canbe executable by the processor 304 to discover a feature enablementinformation management service at the external system 322.

The BIOS hardware 306 also includes communication instructions 314 thatare executable by the processor 304 to send the key license 310 to theexternal system 322. In addition, the communication instructions 314 areexecutable by the processor 304 to request the key license 310, asimilar key license related to the feature, or another key licenserelated to another feature, in response to a request received at theserver 302 for a feature. The BIOS hardware 306 includes featureinstructions 316 that are executable by the processor 304 to provide therequested feature to a requesting system after the key license relatedto the requested feature is received from the external system 322.Further, the feature instructions 316 are executable by the processor304 to not provide the requested feature to the requesting system whenthe key license is not received from the external system 322, such aswhen a maximum number of key licenses for the feature are being used. Inan illustrative embodiment, the feature instructions 316 can beexecutable by the processor 304 to send an error message to therequesting system when the key license is not received.

The external system 322 includes processor 324, memory 326 accessible tothe processor 324, and a network/server interface 328. In oneembodiment, the network/server interface 328 can be a network interfacewhen the external system 322 includes a feature enablement informationmanagement system server. In another embodiment, the network/serverinterface 328 can be a server interface when the external system 322includes a chassis management system.

In a particular embodiment, the memory 326 can include instructions thatare executable by the processor 324 to perform various functions withrespect to managing feature enablement information. In otherembodiments, the external system 322 can include hardware, software, orany combination thereof, adapted to provide the various functionsdescribed.

For example, the memory 326 can include discovery instructions 330 thatare executable by the processor 324 to detect a deployed informationhandling system, such as the information handling system 302. In oneembodiment, the discovery instructions 330 can be executable by theprocessor 324 to discover the information handling system 302. Inanother embodiment, the discovery instructions 330 can be executable bythe processor 324 to detect the information handling system 302 inresponse to an indication received from the information handling system302.

In addition, the memory 326 can include send/receive instructions thatare executable by the processor 324 to receive the key license 310 (orother feature enablement information) from the information handlingsystem 302 and to store the key license 310 at the data store 334. Thekey license 310 is associated at the data store 334 with a feature thatthe information handling system 302 is adapted to provide and can alsobe associated with a particular customer or other party related to theinformation handling system 302.

In a particular embodiment, the memory 326 includes trackinginstructions that are executable by the processor 324 to adjust amaximum number of key licenses for the feature that are available to acustomer or other party related to the information handling system 302.In a particular embodiment, the license tracking instructions areexecutable by the processor 324 to determine, in response to a requestreceived at the external system 322 for a key license, whether a maximumnumber of key licenses is being used for the feature by the partyassociated with a requesting system. The request can be received fromthe information handling system 302 or another requesting system. Thesend/receive instructions 332 are executable by the processor 324 toprovide the requested key license to the requesting system when fewerthan a maximum number of key licenses are being used for the feature bya party associated with the requesting system, and to not provide therequested key license when a maximum number of key licenses is beingused for the feature by the party associated with the requesting system.

FIG. 4 illustrates a particular embodiment of a method of managingfeature enablement in an information handling system. At block 400, aninformation handling system, such as a blade server or other server,powers on. For instance, the information handling system can power onafter being deployed in a server chassis. Moving to block 402, theinformation handling system discovers a feature enablement informationmanagement system via a network. In one embodiment, the informationhandling system can communicate with the network directly. In anotherembodiment, the information handling system can communicate with thenetwork via an interface to the network at the chassis or via a chassismanagement system.

Proceeding to block 404, the information handling system sends featureenablement information to the feature enablement information managementsystem via the network. The feature enablement information is stored atnon-volatile memory at the information handling system prior todeployment. Further, the feature enablement information is associatedwith a feature that the information handling system is adapted toprovide. Continuing to decision node 406, the information handlingsystem determines whether it has received a request for a feature. Thefeature can be associated with the feature enablement information sentto the feature enablement information management system at block 404 orcan be another feature.

If the information handling system has received such a request, themethod advances to 408, and the information handling system requestsfeature enablement information related to the requested feature from thefeature enablement information management system. At decision node 410,the information handling system determines whether it has received fromthe feature enablement information management system the featureenablement information related to the requested feature. If theinformation handling system does not receive the feature enablementinformation associated with the requested feature from the featureenablement information management system, the method moves to block 412,and the information handling system can send an error message to asource of the request for the feature, and the information handlingsystem does not provide the feature. The method can then return todecision node 406.

Returning to decision node 410, if the information handling systemdetermines that it has received the feature enablement informationassociated with the requested feature, the method moves to block 414,and the information handling system provides the feature. Proceeding todecision node 416, the information handling system can determine whetherthe feature is no longer being provided. If the feature has not ended,the method returns to decision node 416. Whereas, if the feature is nolonger provided, the feature enablement information can be released tothe feature enablement information management system at 418, and themethod can return to decision node 406.

FIG. 5 illustrates another particular embodiment of a method of managingfeature enablement in an information handling system. At block 500, aninformation handling system, such as a blade server or other server,powers on after being deployed at a server chassis. Feature enablementinformation is stored at non-volatile memory, such as Basic Input/OutputSystem (BIOS) hardware, at the information handling system prior todeployment. Further, the feature enablement information is associatedwith a feature that the information handling system is adapted toprovide. Moving to block 502, the information handling system discoversa feature enablement information management service at a chassismanagement system at the server chassis. Proceeding to block 504, theinformation handling system sends feature enablement information to thechassis management system (CMS) where it can be stored.

Continuing to decision node 506, the information handling systemdetermines whether it has received a request for a feature. If theinformation handling system has received such a request, the methodadvances to 508, and the information handling system requests featureenablement information related to the requested feature, such as thefeature enablement information sent at block 504, from the CMS (e.g.,via the feature enablement information management service). At decisionnode 510, the information handling system determines whether it hasreceived from the CMS the feature enablement information related to therequested feature. If the information handling system does not receivethe feature enablement information related to the requested feature fromthe CMS, the method moves to block 512, and the information handlingsystem can send an error message to a source of the request for thefeature, and the information handling system does not provide thefeature. The method can then return to decision node 506.

Returning to decision node 510, if the information handling systemdetermines that it has received the feature enablement informationassociated with the requested feature, the method moves to block 514,and the information handling system provides the feature. Proceeding todecision node 516, the information handling system can determine whetherthe feature is no longer provided. If the feature has not ended, themethod returns to decision node 516. Whereas, if the feature is nolonger provided, the feature enablement information can be released tothe CMS at 518, and the method can return to decision node 506.

FIG. 6 illustrates an additional particular embodiment of a method ofmanaging feature enablement in an information handling system. At block600, a feature enablement information management system detects aninformation handling system, such as a new server, communicating with anetwork. In one embodiment, the feature enablement informationmanagement system can discover the information handling system. Inanother embodiment, the information handling system can discover thefeature enablement information management system and inform the featureenablement information management system that the information handlingsystem has been deployed at a customer premises, for example.

Moving to block 602, the feature enablement information managementsystem receives a key license from non-volatile memory, such as BasicInput/Output System (BIOS) hardware, at the information handling systemvia the network. Further, the key license is associated with a featurethat the information handling system is adapted to provide. At block604, in a particular embodiment, the feature enablement informationmanagement system can adjust a maximum number of key licenses for thefeature that are available to a customer or other party associated withthe information handling system. Proceeding to decision node 606, thefeature enablement information management system determines whether ithas received a request for the key license. The request can be receivedfrom the information handling system or another requesting system, suchas another information handling system associated with the customer orother party.

If the feature enablement information management system has received arequest for the key license, the method advances to decision node 608,and the feature enablement information management system determineswhether a maximum number of key licenses is being used for the featureby the party associated with the requesting system. If the featureenablement information management system determines that a maximumnumber of key licenses is being used for the feature by the party, themethod moves to block 610 and the feature enablement informationmanagement system denies the key license to the requesting system. In aparticular embodiment, the feature enablement information managementsystem can send an error message to the requesting system. The methodcan then return to decision node 606.

Returning to decision node 608, if the feature enablement informationmanagement system determines that fewer than a maximum number of keylicenses are being used for the feature by the party, the method movesto block 612, and the feature enablement information management systemprovides the key license to the requesting system. Proceeding todecision node 614, the feature enablement information management systemincrements a number of key licenses used for the feature by the party.In an illustrative embodiment, the method can continue to decision node616, and the feature enablement information management system candetermine whether the key license has been released back to the featureenablement information management system by the requesting system. Ifso, the method can advance to block 618, and the feature enablementinformation management system can decrement the number of key licensesused for the feature by the party.

FIG. 7 illustrates a further particular embodiment of a method ofmanaging feature enablement in an information handling system. At block700, a chassis management system (CMS) at a chassis detects aninformation handling system, such as a new server, that has beendeployed at the chassis. In one embodiment, the CMS can discover theinformation handling system when the information handling system isdeployed at the chassis. In another embodiment, the information handlingsystem can discover the CMS and inform the CMS that the informationhandling system has been deployed at the chassis.

Moving to block 702, the CMS receives a key license from non-volatilememory, such as Basic Input/Output System (BIOS) hardware, at theinformation handling system, e.g., via a feature enablement informationmanagement service provided at the CMS. The key license is associatedwith a feature that the information handling system is adapted toprovide. At block 704, in a particular embodiment, the CMS can adjust amaximum number of key licenses for the feature that are available toinformation handling systems deployed at the chassis. For instance, theCMS can set the maximum number at one or increment a previous maximumnumber by one.

Proceeding to decision node 706, the CMS determines whether it hasreceived a request for the key license. The request can be received fromthe information handling system or another requesting system, such asanother information handling system at the chassis. If the CMS hasreceived a request for the key license, the method advances to decisionnode 708, and the CMS determines whether a maximum number of keylicenses are being used for the feature by information handling systemsat the chassis. If the CMS determines that a maximum number of keylicenses is being used, the method moves to block 710 and the CMS deniesthe key license to the requesting system. In a particular embodiment,the CMS can send an error message to the requesting system. The methodcan then return to decision node 706.

Returning to decision node 708, if the CMS determines that fewer than amaximum number of key licenses are being used for the feature, themethod moves to block 712, and the CMS provides the key license to therequesting system. Proceeding to decision node 714, the CMS increments anumber of key licenses used for the feature by information handlingsystems at the chassis. In an illustrative embodiment, the method cancontinue to decision node 716, and the CMS can determine whether the keylicense has been released back to the CMS by the requesting system. Ifso, the method can advance to block 718, and the CMS can decrement thenumber of key licenses used for the feature by information handlingsystems at the chassis.

Note that not all of the activities described above in the generaldescription or the examples are required, that a portion of a specificactivity may not be required, and that one or more further activitiesmay be performed in addition to those described. Still further, theorder in which activities are listed are not necessarily the order inwhich they are performed.

The specification and illustrations of the embodiments described hereinare intended to provide a general understanding of the structure of thevarious embodiments. The specification and illustrations are notintended to serve as an exhaustive and comprehensive description of allof the elements and features of apparatus and systems that use thestructures or methods described herein. Many other embodiments may beapparent to those of skill in the art upon reviewing the disclosure.Other embodiments may be used and derived from the disclosure, such thata structural substitution, logical substitution, or another change maybe made without departing from the scope of the disclosure. Accordingly,the disclosure is to be regarded as illustrative rather thanrestrictive.

According to a first aspect, a system to manage feature enablement in aninformation handling system includes an information handling systemincluding an information handling system including non-volatile memoryaccessible to a processor. The non-volatile memory stores featureenablement information related to a feature that the informationhandling system is adapted to provide. The non-volatile memory alsostores instructions that are accessible to the processor and executableby the processor to send feature enablement information related to thefeature to an external system after the information handling system isdeployed and to request the feature enablement information, or otherfeature enablement information related to the feature, from the externalsystem in response to receiving a request for the feature.

In an embodiment of the first aspect, the non-volatile memory comprisesbasic input/output system (BIOS) hardware. In another embodiment of thefirst aspect, the external system comprises a feature enablementinformation management system communicating remotely with theinformation handling system via a network. In yet another embodiment ofthe first aspect, the external system comprises a chassis managementsystem local to the information handling system. In still anotherembodiment of the first aspect, the non-volatile memory storesinstructions that are accessible to the processor and executable by theprocessor logic to detect the external system after the informationhandling system is deployed.

In an additional embodiment of the first aspect, the non-volatile memorystores instructions that are accessible to the processor and executableby the processor to provide the requested feature after receiving thefeature enablement information, or the other feature enablementinformation related to the feature, at the information handling system;and not provide the feature to the requesting system after the featureenablement information, or the other feature enablement informationrelated to the feature, is denied by the external system. In a furtherembodiment of the first aspect, the non-volatile memory storesinstructions that are accessible to the processor and executable by theprocessor to release the feature enablement information, or the otherfeature enablement information related to the feature, to the externalsystem after the feature is no longer provided.

In another embodiment of the first aspect, the feature enablementinformation can include a key license. In a further embodiment of thefirst aspect, the feature enablement information can include a digitalcertificate, a password, a software token, or any combination thereof.

According to a second aspect, a method of managing feature enablement inan information handling system includes receiving feature enablementinformation from non-volatile memory at an information handling system.The feature enablement information relates to a feature that theinformation handling system is adapted to provide. The method alsoincludes storing the feature enablement information and receiving arequest for the feature enablement information from a requesting systemthat is adapted to provide the feature. In an embodiment of the secondaspect, the feature enablement information includes a key license andthe method includes determining whether a maximum number of key licensesrelated to the feature are not being used before sending the key licenseto the requesting system; sending the key license to the requestingsystem when fewer than the maximum number of key licenses are beingused; and denying the key license when the maximum number of keylicenses are being used.

In another embodiment of the second aspect, the method also includesincrementing a number of key licenses being used for the feature aftersending the key license to the requesting system. In yet anotherembodiment of the second aspect, the method includes decrementing thenumber of key licenses being used for the feature after the key licenseis released by the requesting system. In an additional embodiment of thesecond aspect, the requesting system is the information handling system.Alternatively, the requesting system can be another information handlingsystem.

In yet another embodiment of the second aspect, the method includesdetecting the information handling system. Further, the method canincludes sending to the information handling system an instruction tosend the feature enablement information to the external system beforereceiving the feature enablement information.

According to a third aspect, a computer-readable medium includingprocessor-readable instructions that are executable by a processor toperform a method. The method includes sending feature enablementinformation related to a feature from an information handling system toan external system after the information handling system is deployed,where the feature enablement information is stored at non-volatilememory at the information handling system. The method also includesrequesting the feature enablement information, or other featureenablement information related to the feature, from the external systemin response to receiving a request for the feature.

In an embodiment of the third aspect, the feature includes application,a utility, a service, an upgrade, or any combination thereof. In yetanother embodiment of the third aspect, the method includes receivingfrom the external system an instruction to send the feature enablementinformation to the external system before sending the feature enablementinformation.

Certain features are, for clarity, described herein in the context ofseparate embodiments, may also be provided in combination in a singleembodiment. Conversely, various features that are, for brevity,described in the context of a single embodiment, may also be providedseparately or in any subcombination. Further, reference to values statedin ranges includes each and every value within that range.

Benefits, other advantages, and solutions to problems have beendescribed above with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any feature(s) that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeature of any or all the claims.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

1. A system to manage feature enablement in an information handlingsystem, the system comprising: an information handling system includingnon-volatile memory accessible to a processor, wherein the non-volatilememory stores feature enablement information related to a feature thatthe information handling system is adapted to provide, and wherein thenon-volatile memory stores instructions that are accessible to theprocessor and executable by the processor to: send the featureenablement information related to the feature to an external systemafter the information handling system is deployed; and request thefeature enablement information, or other feature enablement informationrelated to the feature, from the external system in response toreceiving a request for the information handling system to provide thefeature.
 2. The system of claim 1, wherein the non-volatile memorycomprises platform-level hardware that stores firmware information. 3.The system of claim 2, wherein the non-volatile memory comprises basicinput/output system (BIOS) hardware.
 4. The system of claim 1, whereinthe external system comprises a feature enablement informationmanagement system communicating remotely with the information handlingsystem via a network.
 5. The system of claim 1, wherein the externalsystem comprises a chassis management system local to the informationhandling system.
 6. The system of claim 1, wherein the non-volatilememory stores instructions that are accessible to the processor andexecutable by the processor to detect the external system after theinformation handling system is deployed.
 7. The system of claim 1,wherein the non-volatile memory stores instructions that are accessibleto the processor and executable by the processor to: provide therequested feature after receiving the feature enablement information, orthe other feature enablement information related to the feature, at theinformation handling system; and not provide the feature after thefeature enablement information, or the other feature enablementinformation related to the feature, is denied by the external system. 8.The system of claim 1, wherein the non-volatile memory storesinstructions that are accessible to the processor and executable by theprocessor to release the feature enablement information, or the otherfeature enablement information related to the feature, to the externalsystem after the feature is no longer provided.
 9. The system of claim1, wherein the feature enablement information comprises a key license, adigital certificate, a password, a software token, or any combinationthereof.
 10. A method of managing feature enablement in an informationhandling system, the method comprising: receiving feature enablementinformation from non-volatile memory at an information handling system,wherein the feature enablement information relates to a feature that theinformation handling system is adapted to provide; storing the featureenablement information; and receiving a request for the featureenablement information from a requesting system that is adapted toprovide the feature.
 11. The method of claim 10, wherein the featureenablement information comprises a key license, and wherein the methodfurther comprises: determining whether a maximum number of key licensesrelated to the feature are not being used before sending the key licenseto the requesting system; sending the key license to the requestingsystem when fewer than the maximum number of key licenses are beingused; and denying the key license when the maximum number of keylicenses is being used.
 12. The method of claim 11, further comprisingincrementing a number of key licenses being used for the feature aftersending the key license to the requesting system.
 13. The method ofclaim 12, further comprising decrementing the number of key licensesbeing used for the feature after the key license is released by therequesting system.
 14. The method of claim 10, wherein the requestingsystem is the information handling system.
 15. The method of claim 10,wherein the requesting system is another information handling system.16. The method of claim 10, further comprising detecting the informationhandling system.
 17. The method of claim 16, further comprising, beforereceiving the feature enablement information, sending to the informationhandling system an instruction to send the feature enablementinformation to the external system.
 18. A computer-readable mediumincluding processor-readable instructions that are executable by aprocessor to perform a method, the method comprising: sending featureenablement information related to a feature from an information handlingsystem to an external system after the information handling system isdeployed, wherein the feature enablement information is stored atnon-volatile memory at the information handling system; and requestingthe feature enablement information, or other feature enablementinformation related to the feature, from the external system in responseto receiving a request for the feature.
 19. The computer-readable mediumof claim 18, wherein the feature includes an application, a utility, aservice, an upgrade, or any combination thereof.
 20. Thecomputer-readable medium of claim 18, wherein the method includesreceiving from the external system an instruction to send the featureenablement information to the external system before sending the featureenablement information.